canonical: https://jentic.com/apis/swaggerhub.nexus-gg/nexusgg-creator-program-api

# Nexus.gg Creator Program API

Seamlessly integrate the Nexus creator program into your native checkout process. The API exposes 21 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get creator groups and their group ids, generate a code for a player. if the playerid specified has already been linked . Covers 21 operations with apiKey authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Get creator groups and their group ids
- Generate a code for a player. If the playerId specified has already been linked
- Return all members of a group and their member details, including unique id and
- Update
- Monitor Nexus.gg Creator Program API operational status and events

## Use cases

### Payments Operations

Use the Nexus.gg Creator Program API to perform payments operations programmatically. The API provides 21 endpoints covering core functionality including get creator groups and their group ids, generate a code for a player. if the playerid specified has already been linked , return all members of a group and their member details, including unique id and .

Example prompt: Call GET `/manage/groups` to get creator groups and their group ids

### Automated Attributions Management

Automate attributions operations by combining multiple Nexus.gg Creator Program API endpoints. Agents can generate a code for a player. if the playerid specified has already been linked  and then return all members of a group and their member details, including unique id and  in a single workflow.

Example prompt: Call POST `/manage/members` to generate a code for a player. if the playerid specified has already been linked , then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Nexus.gg Creator Program API 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 apiKey tokens manually.

Example prompt: Search Jentic for 'get creator groups and their group ids', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/manage/groups` | Get creator groups and their group ids |
| POST | `/manage/members` | Generate a code for a player. If the playerId specified has already been linked |
| GET | `/manage/members` | Return all members of a group and their member details, including unique id and |
| GET | `/manage/members/{memberCode}` | Get a member and their details by code |
| GET | `/manage/members/id/{memberId}` | Get a member and their details by member id |
| GET | `/manage/members/player/{playerId}` | Get a member and their details by your internal playerId |
| POST | `/manage/members/player/{playerId}/metadata` | Update |
| POST | `/manage/members/link` | Link an existing nexus to your creator group using an authCode |

## Key resources

- **Attributions** — Operations for attributions
- **Manage** — Operations for manage

## Why Jentic

- **Setup:** Wiring the Nexus.gg Creator Program API by hand means setting the X-SHARED-SECRET header on every request and tracking public versus private key usage yourself. Through Jentic you install once, import the Nexus.gg Creator Program API from the API Directory, store the shared secret once, and your agent calls it.
- **Permission scoping:** Nexus.gg puts the member and player id in the URL path (`/manage/members/{memberCode}` and `/manage/members/player/{playerId}`), so a rule can pin your agent to one member. You choose the operations it may call, so it can stay on reading groups and member details while creating or linking members is not included unless you add it.
- **Credential handling:** Your Nexus.gg shared secret is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get creator groups' or 'look up a member by player id', and Jentic returns the matching Nexus.gg Creator Program API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Nexus.gg Creator Program API use?

The Nexus.gg Creator Program API uses an API key passed in the `X-SHARED-SECRET` header. 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 get creator groups and their group ids with the Nexus.gg Creator Program API?

Yes. Use the GET `/manage/groups` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Nexus.gg Creator Program API?

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 get creator groups and their group ids through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get creator groups and their group ids'. Jentic returns the matching Nexus.gg Creator Program API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Nexus.gg Creator Program API have?

The Nexus.gg Creator Program API exposes 21 endpoints covering attributions, manage operations.

### Can I limit what my agent is allowed to do with the Nexus.gg Creator Program API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Nexus.gg operations and credentials the agent may use. You can keep it to read-only calls like GET `/manage/groups` and GET `/manage/members` while excluding write operations such as POST `/manage/members` or POST `/manage/members/link.` Because Nexus.gg puts the member code and player id in the URL path, a rule can also pin the agent to a single member or player.