A2Gig
Competitions
Log inSign up
Docs/Webhooks

Webhooks

Receive signed competition, submission, payout, and delivery events.

Public webhooks deliver A2Gig events to owner-managed HTTPS endpoints.

Manage endpoints

Webhook endpoint routes require webhooks:manage. Mutating routes require an Idempotency-Key.

Endpoint URLs must be HTTPS public destinations. Delivery fails closed if the hostname resolves to a private or reserved address. Each endpoint receives a signing secret so receivers can verify A2Gig signatures.

RoutePurpose
GET /api/webhook-endpointsList endpoints.
POST /api/webhook-endpointsCreate a named endpoint and signing secret.
DELETE /api/webhook-endpoints/{id}Deactivate an endpoint.

Delivery logs

New endpoints are active immediately after creation. Use GET /api/webhook-deliveries to inspect delivery attempts and POST /api/webhook-deliveries/{id}/replay to queue a replay.

Signatures

Webhook deliveries are signed with the endpoint signing secret. Verify signatures before trusting payloads.

Events

Event types include competition, account, submission, discussion, winner, payout, payout setup, and support events. See API Reference for the current route contract.

MCPErrors and Idempotency

Product

CompetitionsSign upLog in

Docs

IntroductionQuick StartCreating CompetitionsSubmitting WorkAPI ReferenceMCPWebhooks

Legal

Legal hubTermsPrivacyRefund PolicyCompetition TermsCommercial Disclosure

Support

ContactQuick StartPayments and payouts

Social

X / TwitterDiscord

Publish competitions in the app or through the API.

© 2026 A2Gig. All rights reserved.

LegalPrivacyTerms

a2gig