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

# Nexus.gg Bounty API

Nexus bounties allow you to reward your creators for their participation in the referral program. The API exposes 14 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list bounties, retrieve information on a bounty. progress information will only be included whe. Covers 14 operations with apiKey authentication.

## Scope

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

## Capabilities

- List bounties
- Retrieve information on a bounty. Progress information will only be included whe
- Log an event occurence, by the event code
- Get all events for a creator group
- Delete an event
- Bulk logging of up to 1000 events at once

## Use cases

### Developer Tools Operations

Use the Nexus.gg Bounty API to perform developer tools operations programmatically. The API provides 14 endpoints covering core functionality including list bounties, retrieve information on a bounty. progress information will only be included whe, log an event occurence, by the event code.

Example prompt: Call GET / to list bounties

### Automated Complete Reward Management

Automate complete reward operations by combining multiple Nexus.gg Bounty API endpoints. Agents can retrieve information on a bounty. progress information will only be included whe and then log an event occurence, by the event code in a single workflow.

Example prompt: Call GET /{bountyId} to retrieve information on a bounty. progress information will only be included whe, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Nexus.gg Bounty 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 'list bounties', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/` | List bounties |
| GET | `/{bountyId}` | Retrieve information on a bounty. Progress information will only be included whe |
| POST | `/event` | Log an event occurence, by the event code |
| GET | `/event` | Get all events for a creator group |
| DELETE | `/event/{eventId}` | Delete an event |
| POST | `/event/bulk` | Bulk logging of up to 1000 events at once |
| GET | `/event/bulk/{bulkOperationId}` | Get the status of a Create Event bulk operation |
| POST | `/event/add-referral-code` | Updates all existing events for a given playerId are not associated with a refer |

## Key resources

- **Complete Reward** — Operations for complete reward
- **Event** — Operations for event
- **Member** — Operations for member
- **Rewards** — Operations for rewards

## Why Jentic

- **Setup:** Wiring the Nexus.gg Bounty API by hand means setting the X-SHARED-SECRET header on every request and managing the public, private, and variable key variants yourself. Through Jentic you install once, import the Nexus.gg Bounty API from the API Directory, store the shared secret once, and your agent calls it.
- **Permission scoping:** Nexus.gg puts the bounty and event id in the URL path (/{bountyId} and `/event/{eventId}`), so a rule can pin your agent to one bounty. You choose the operations it may call, so it can stay on listing bounties and reading events while destructive ones like event deletion are not included unless you add them.
- **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 'list bounties' or 'record a bounty event', and Jentic returns the matching Nexus.gg Bounty API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Nexus.gg Bounty API use?

The Nexus.gg Bounty 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 list bounties with the Nexus.gg Bounty API?

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

### What are the rate limits for the Nexus.gg Bounty 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 list bounties through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list bounties'. Jentic returns the matching Nexus.gg Bounty API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Nexus.gg Bounty API exposes 14 endpoints covering complete reward, event, member operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Nexus.gg Bounty operations and credentials the agent may use. Because the bounty and event IDs sit in the URL path (/{bountyId} and `/event/{eventId}`), a rule can pin the agent to a single bounty and keep it on read-only calls like GET / to list bounties and GET /event to read events. Destructive operations such as DELETE `/event/{eventId}` stay off limits unless you explicitly grant them, and the shared secret is injected at execution time rather than exposed to the agent.