# Developer portal introduction

The [Developer portal](https://developers.spotnana.com) provides partners, clients, and their developers with a secure, self-service resource for common developer tasks. The portal supports API token management, webhook management, debugging, audit logs, and provides access to API documentation. It also applies the roles defined in the [Roles-based Access Control (RBAC)](/spotnana/basic_rbac_concepts) model to restrict the permissions granted to developers (e.g., which organizations they can view in the portal).

For details on how to perform common API tasks and to access reference information, see Spotnana [Developer documentation](/).

## Audience

- TMC and partner developers building or maintaining integrations with Spotnana APIs.
- Company-specific developers at enterprise clients managing their own API credentials and webhook subscriptions.


## Prerequisites

To gain access to the Developer portal, you should contact Spotnana to have us provision you with the necessary roles. These roles will be permissioned so that you can only perform actions for your organization or the organizations to which your TMC grants you access. Spotnana must also enable access for each organization.

The [roles](/spotnana/basic_rbac_concepts#roles) you must have are:

- **Developer Portal (Read only)**
  - Able to view keys, webhook subscriptions, and delivery logs. Cannot create or modify. This role is self-assignable by the TMC Admin within the OBT (TMC Admins can assign it to themselves). You can also use the [roles](/openapi/rbacapi/roles) APIs to assign it.
- **Developer Portal Administrator (Read and Write)**
  - Able to create, view, and revoke API keys and configure webhooks. This role is self-assignable by the TMC Admin within the OBT (TMC Admins can assign it to themselves). You can also use the [roles](/openapi/rbacapi/roles) APIs to assign it.


### Login

The Developer portal uses the same SSO credentials as the Spotnana OBT (Okta or Azure AD). There are no new credentials to manage.
Access the developer portal using the URL: [https://developers.spotnana.com](https://developers.spotnana.com)

To access the non-production environment, use the **Live** / **Sandbox** toggle on the login page, or go directly to [https://developers.partners.spotnana.com](https://developers.partners.spotnana.com).

## Setting context in the portal

Two settings control which information you will view or edit in the portal:

1. **Environment toggle (Live or Sandbox):**
  - Every action in the portal is scoped to the selected environment. For example, a key created in *Sandbox* does not exist in *Live*.
2. **Company selector:**
  - The menu at the top determines which company or organization you are creating keys and webhook subscriptions for. You only see the companies your roles and groups grant you access to.


## Actions you can perform (by section)

The information you can view and the various actions you can perform in the portal are described in the table below.

| Area  | What it does  |
|  --- | --- |
| Dashboard | At-a-glance counts of your active access keys and webhook subscriptions as well as recent activity. |
| Access Keys | The ability to create, view, and revoke API client tokens. Each key shows its client ID, the company it belongs to, its access level (*TMC Admin* or *Company Admin*), who created it, and when. The secret is displayed once at creation with a copy prompt, then masked permanently. |
| Webhook Subscriptions | The ability to register webhook endpoints, enable, test, or disable them, and configure HMAC SHA-256 authentication. Multiple subscriptions per company are supported. |
| Event Logs | The ability to view and filter delivery logs within a 3 month retention window. Filter by date range, tripId, pnrId, subscription, and HTTP status to see exactly what was delivered, when, and whether it succeeded. |
| Webhook Replay | The ability to replay any historical webhook event, event type, and a specific time range (within the retention window). Bulk replay up to 5,000 events at a time. No need to contact Spotnana to resend missed events. See [Replay webhook deliveries](/integration/dev-platform/replay-webhook-deliveries) for more details. |
| Documentation | Access to full API reference (Auth, Users, Company, Policy, Trip, Air, Hotel, Events, and Payments), onboarding guides, general concepts, workflows, webhook documentation, and changelogs at [https://developers.spotnana.com/docs](https://developers.spotnana.com/docs). You can also use AI-powered search (Ctrl+K). |


## Sample configuration for your third-party partners

If a third-party partner needs API access to service your customers, the recommended configuration is to set up a dedicated partner organization inside your TMC. This is done by following the steps in the table below (each step also states who the step is performed by).

| Step  | Done by  | Action  |
|  --- | --- | --- |
| 1 | TMC admin | Create a dedicated organization for the partner inside your TMC. The name should describe the pairing (e.g., `PARTNER - TMC NAME`). This organization exists to contain the identities of your partner company's developers. It is not a travel organization. |
| 2 | TMC admin | Create user profiles in that organization for each of the partner company's developers (use their names). |
| 3 | TMC admin | Create an [RBAC user group](/spotnana/basic_rbac_concepts#user-groups) in that organization (e.g., **Developer Access**) and add the partner company's developer profiles to it. Assign the following roles to that user group:* the **Developer Portal Administrator** [role](/spotnana/basic_rbac_concepts#available-roles), scoped to the customer organizations that the partner services.
* any additional roles the partner developers will require.

 |
| 4 | The partner company developers | The partner company developers must then log in to the Spotnana [Developer portal](https://developers.spotnana.com/) with their own credentials and perform any actions they require. For example, create API users, generate access keys, and create webhook subscriptions for the client companies they have been scoped to service. |
| 5 | TMC admin | As the partner onboards more of your customers, add those organizations to the group's scope. No new setup is needed on the partner side. |


## Webhook migration

Partners currently on Webhook V1 (legacy) must migrate to V2 to access [Developer portal](https://developers.spotnana.com/) features such as delivery logs, event replay, and self-serve webhook management.

### What to expect

- Spotnana performs the migration. No changes are required to your API endpoints or credentials.
- Migration happens in non-production environment first, then in production, to ensure no event loss.
- Your event volume will be monitored closely throughout the cutover window.


Action needed before your migration is scheduled
Please confirm with your Spotnana contact whether your team (or any of your partners) are currently running webhook tests in your non-production (e.g., sandbox or staging) environment. Active test traffic must be accounted for before scheduling.