Typed contract
Documented endpoints and examples make supported requests and responses clear.
Developer API
Automate link operations through the same validated contracts.
The Gods.ly API follows a published OpenAPI specification. Automated tools receive the same workspace checks, input validation, retry protection, and status rules as the dashboard.
Open integrationsScoped access
API-key metadata records explicit permissions and never returns stored plaintext secrets.
Predictable errors
Standard error responses explain invalid fields and include a request ID for support.
Retry without creating duplicates
Create requests can include a unique retry key. If a connection times out, the same request can be sent again without publishing the same asset twice.
Version checks stop one update from silently overwriting a newer change from another person or process.
Keep every workspace separate
Credentials are tied to an identity and workspace. The server verifies membership, permission, ownership, and current status for every request.
Guessing an identifier from another workspace is never enough to view or change that resource.
Evolve without silent breakage
The generated client and schema compatibility checks make contract changes visible during builds. Additive fields remain safe while breaking changes require a versioned migration path.
Create and manage scoped API keys in the developer workspace. Revoke unused keys and keep active secrets in a trusted environment.
Common questions
What teams ask before they start.
Is there a generated client?
Yes. The API documentation includes supported client examples and the current OpenAPI contract.
Where can I manage API credentials?
Use the developer workspace to create scoped keys, review their permissions, and revoke access when an integration is retired.
Start with a real workflow