canonical: https://jentic.com/apis/swaggerhub.rapidsos-api/authentication-token-for-ingress-and-egress-apis

# Rapidsos Api Authentication Token for Ingress and Egress APIs

These HTTPS endpoints are used to obtain a token that allows partners to push or request data from the RapidSOS Emergency Data Platform API endpoints. The API exposes 2 endpoints.

## For AI agents

Programmatically post-oauth-token, post-oauth-v2-token. Covers 2 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- post-oauth-token
- post-oauth-v2-token
- Integrate Authentication Token for Ingress and Egress APIs into automated workflows
- Query and filter Authentication Token for Ingress and Egress APIs records by parameters
- Monitor Authentication Token for Ingress and Egress APIs operational status and events

## Use cases

### Identity and Authentication Operations

Use the Authentication Token for Ingress and Egress APIs to perform identity auth operations programmatically. The API provides 2 endpoints covering core functionality including post-oauth-token, post-oauth-v2-token.

Example prompt: Call POST /oauth/token to post-oauth-token

### Data Retrieval and Monitoring

Query Authentication Token for Ingress and Egress APIs resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Authentication Token for Ingress and Egress APIs endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Authentication Token for Ingress and Egress APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'post-oauth-token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /oauth/token | post-oauth-token |
| POST | /oauth/v2/token | post-oauth-v2-token |

## Key resources

- **Client Credential Grant Flow** — Operations related to Client Credential Grant Flow
- **Password Grant Flow** — Operations related to Password Grant Flow

## Why Jentic

- **Setup:** Wiring the Authentication Token for Ingress and Egress APIs by hand means coding its two OAuth token endpoints against the correct rapidsos.com environment host and handling retries yourself. Through Jentic you install once, import the Authentication Token for Ingress and Egress APIs from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** This API carries its client credentials in the request body of the token operations, not in the URL path, so you limit the agent to the operations it needs, such as the v2 token endpoint, and leave out the other unless you add it. Every operation the agent can call is one you chose to allow.
- **Credential handling:** Your client credentials for the Authentication Token for Ingress and Egress APIs are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'obtain an OAuth access token', and Jentic returns the matching Authentication Token for Ingress and Egress APIs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Authentication Token for Ingress and Egress APIs use?

The Authentication Token for Ingress and Egress APIs uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I post-oauth-token with the Authentication Token for Ingress and Egress APIs?

Yes. Use the POST /oauth/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Authentication Token for Ingress and Egress APIs?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I post-oauth-token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'post-oauth-token'. Jentic returns the matching Authentication Token for Ingress and Egress APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Authentication Token for Ingress and Egress APIs have?

The Authentication Token for Ingress and Egress APIs exposes 2 endpoints covering client credential grant flow, password grant flow operations.

### Can I limit what my agent is allowed to do with the Authentication Token for Ingress and Egress APIs?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's two token operations the agent may call, so you can grant only POST /oauth/v2/token and leave out POST /oauth/token unless you add it. Every operation the agent can reach is one you chose to allow. Since the client credentials travel in the request body of these token calls rather than in the URL, they are stored once by your own instance and injected at execution time instead of being exposed to the agent.