The Pro developer tools let a server-side integration read schedules and
availability, request delivery reschedules, mark pickups ready, and receive
delivery scheduling events. Development plans include Pro access.
API credentials
Open Settings → Developer → API and refresh the status.
Confirm API access is enabled in the current environment.
Enter a credential name and select only the permissions required.
Create the credential and copy the token immediately. Store it in a server
secret manager, never storefront code or a browser application.Open the API documentation from the displayed base URL.
For write actions, read the order first, send its current revision and a
unique idempotency key, then poll the returned operation until it completes.
A 202 response means the action is queued, not completed. Availability is
advisory and does not reserve capacity or confirm cart/address eligibility.
Outbound webhooks
Open Settings → Developer → Webhooks.
Add a public HTTPS endpoint on port 443 without URL passwords or query
strings.Select
delivery_scheduled,pickup_ready, or both, and optionally limit
delivery to one location.Copy the signing secret when it is shown and verify signatures on your
server.Send a test event, then refresh status and review the delivery result.
New endpoints receive future events only. pickup_ready is an app status; it
does not fulfill the Shopify order or notify the customer.
Troubleshooting
API credentials
Select Refresh status before changing credentials. If the page says API
access is disabled in the environment, contact RP support; regenerating a
credential will not enable the service.A token is displayed only when it is created. If it was not stored safely,
revoke it and create a replacement rather than asking support to recover it.For a
401or403, confirm the token is active and has the required
permission. Do not add unrelated permissions as a troubleshooting shortcut.For a
409, read the order again and retry with its current revision. For a
queued202, poll the operation instead of submitting the same change with a
new idempotency key.Contact RP support with the timestamp, HTTP method and path, response status,
request or operation ID, and a redacted response body. Never send the token.
Outbound webhooks
Select Refresh webhook status, then use the built-in test event. Review
the displayed delivery result and your endpoint logs for the same time.Confirm the endpoint is public HTTPS on port 443, responds promptly, and does
not require credentials in its URL.Verify the signature against the unmodified request body before parsing it.
If the signing secret is lost or exposed, rotate it rather than requesting
its current value.A successful test does not replay earlier events. New and re-enabled
endpoints receive future matching events only.Contact the endpoint owner for DNS, TLS, firewall, timeout, or application
errors. Contact RP support when the app records no delivery attempt for an
eligible future event.
Important warnings or limitations
These tools are for developers who can securely operate an HTTPS service.
Revoke a credential or rotate a webhook secret immediately if it is exposed.
API and webhook features require Pro and can also be disabled by environment.
Revoking a credential or losing Pro access stops queued actions.
Customer contact information is excluded from the API described here.
Do not place tokens or signing secrets in URLs, browser applications,
storefront JavaScript, screenshots, logs, or support messages.