StrideHQ API documentation

The StrideHQ API follows REST design. Resources (creators, invoices, POs, payment runs, payments) have predictable addresses, which also set the sections of the API reference. Requests and responses are JSON, and standard HTTP status codes tell you what happened. An OpenAPI 3.1 spec is generated from the code, so you can generate a client in your language or import it into Postman.

API access is set up as part of your StrideHQ onboarding. Request access to get started.

To get familiar with the basics of the StrideHQ API, continue to Getting started, or jump straight to making your first request.

Every request needs an API key with the right scopes. To learn more, go to Authentication. You can also read about each scope in Scopes.

If something isn't working, go to Errors and troubleshooting for what could have gone wrong and how to fix it.

Every payment run still needs a person to approve it in StrideHQ. The API can prepare a run, but it can't approve, fund or release one.

This applies to API keys only. The agent's own authority to approve or release runs is set by your Owner in StrideHQ and doesn't extend to the API.