Quickstart
Create an application and sandbox key, try an API in the explorer and run your first Connect flow.
Updated 07/10/2026
On this page
1. Sign in and choose a workspace
Sign in at https://developer.amakoragroup.com. Your first sign-in creates a personal workspace in which you are the owner. To join a team workspace, accept the invitation an administrator sends you. Roles decide what you can do; see Authentication.
2. Create a project
Open Dashboard → Projects and create a project with a name and a short key (2–32 characters, starting with a letter, for example OPS). Projects group your applications, connections and integrations.
3. Create an application
Open Dashboard → Apps → New application:
Choose the application type: server, spa, mobile or service.
Link the project and select the API products the application may use.
Add redirect URIs and allowed origins if it is a browser or mobile app.
New applications start in sandbox mode.
4. Create a sandbox key
On the application, open Keys → Create key. Choose read, write or both. The key looks like ak_sandbox_… and is shown once; store it in a secret manager. Keys can be rotated (a new secret, same key) or revoked at any time.
Sandbox keys authorise requests made through the sandbox API explorer. They are not accepted by the console REST API, which uses your signed-in session token; see Authentication.
5. Try an API in the sandbox explorer
Open Dashboard → API explorer, pick your application, an endpoint of a subscribed API product and, if the endpoint requires it, your sandbox key. Send the request and inspect the status, headers, body and timing. Every request is written to Request logs for the application.
GET and HEAD requests need a key with the read scope; every other method needs write.
6. Connect a system
Open Dashboard → Connect → Connections → New connection:
Choose a provider from the connector directory.
Enter its settings (for example the site, region or account ID). Nexra derives the provider's API origin and refuses any other host.
Enter the credentials. Nexra writes them to a secure vault and stores only the secret reference.
Tick the write operations this connection may perform. Reads are always allowed; writes are opt-in per connection.
Test the connection. A successful test makes it active and lists its available operations.
7. Build and run a flow
Open Connect → New integration or install a template from Connect → Templates.
Add a flow with a manual or scheduled trigger, a source operation and a destination operation.
Map fields. Use Preview to apply the mapping to a sample record before anything is written.
Validate and Publish the flow version.
Run it in sandbox from the flow page and open the run to see each step and record.
To run in production, create a production environment for the integration, deploy the published version and ask another workspace member to approve the deployment. See Approvals and deployments.
Next steps
Use the Nexra MCP server to let an AI agent trigger approved flows.
Webhooks to receive signed event notifications.
API overview to automate the same steps over HTTP.
Connect a provider account across interfaces
See Connect through MCP, APIs, CLI and SDKs for account setup, exact operation selection, authentication, copyable examples, sandbox boundaries and approval troubleshooting.