Markdown
Create an endpoint
Plain Markdown for agents, CLIs, MCP clients, and readers who want a copyable text version.
# Create an endpoint
Canonical: https://docs.flowrelay.app/setup/endpoints/
Markdown: https://docs.flowrelay.app/setup/endpoints.md
An endpoint is the private URL your sender uses to send events into FlowRelay.
## Steps
Complete these in order.
1. Open FlowRelay
Open Shopify Admin, then open FlowRelay from Apps.
2. Name the endpoint
Choose Create endpoint and name it for the sender or workflow, such as Warehouse status to Flow.
3. Set routing fields
Set a clear Source label and default event type, then choose the trigger variant Shopify Flow should receive. Use Generic when no native Shopify reference is needed.
4. Store the endpoint URL privately
Create the endpoint, then copy the endpoint URL only into the sender system or a private setup note.
5. Configure authentication
Continue to authentication before asking the sender to send real events.
6. Verify with a receipt
After the sender sends a test event with synthetic data, use Event history and the receipt to verify accepted, delivered, or failed status.
## Who needs the endpoint URL
Only the sender owner or private sender configuration needs the endpoint URL. Treat it like setup material, not public documentation or a support artifact.
- [Install FlowRelay from the Shopify App Store](https://apps.shopify.com/flowrelay-1): Install FlowRelay before creating your first sender endpoint.
## Set routing identity and trigger shape
Keep Source label, trigger variant, default event type, and resolved event type separate. The Source label identifies the endpoint in Shopify Flow; the trigger variant selects the payload/reference shape; the resolved event type is a mapped value when present or the default otherwise.
- Term: Source label; Meaning: The endpoint routing identity surfaced to Shopify Flow.
- Term: Trigger variant; Meaning: Selects the FlowRelay trigger payload and native-reference shape.
- Term: Default event type; Meaning: The fallback event label used when no mapped event-type path supplies one.
- Term: Resolved event type; Meaning: The mapped event-type value when present; otherwise the endpoint's default event type.
## Success check
After the sender sends a test event with synthetic data, Event history shows a receipt for the expected endpoint. If the event is not visible, verify the sender URL, auth setup, and whether the sender received a FlowRelay response.
## Keep private
Do not put endpoint URLs, generated secrets, full authentication headers, signatures, raw event bodies, Shopify tokens, customer data, or copied incidents into screenshots, tickets, public examples, or chat threads.
## Handoff Boundary
Delivered means FlowRelay handed the trigger to Shopify Flow. It does not mean downstream Shopify Flow branches, app calls, fulfillment changes, emails, or later systems completed.
## Related
- [Authenticate requests](https://docs.flowrelay.app/setup/authentication.md)
- [Trigger variants and mapping](https://docs.flowrelay.app/setup/trigger-variants-and-event-mapping.md)
- [Add the Shopify Flow trigger](https://docs.flowrelay.app/setup/shopify-flow-trigger.md)
- [Send your first test event](https://docs.flowrelay.app/getting-started/first-event.md)
## Safety Boundary
Do not share endpoint secrets, authentication headers, HMAC values, tokens, raw event bodies, customer records, Shopify sessions, store passwords, or database URLs in public examples.
FlowRelay