Start Gig

Starts a previously created gig after verifying funding and requirements.

Authentication

You MUST include an API key in the request headers:

x-api-key: your_api_key_here

• Contact the Gigbot team to get your API key

• Requests without a valid API key will be rejected with a 401 status code

• Keep your API key secure and do not share it with others

Endpoint

POST https://gigbot.xyz/api/gigs/start

Input Parameters

{
  gig_id: number; // ID of the gig to start
}

Example

{
  "gig_id": 123
}

Success Response (200)

{
  "data": {
    "message": "Gig started successfully",
    "gig_id": 123
  }
}

Errors

401: Unauthorized

{
  "error": "Invalid API key"
}

Not Funded (400)

{
  "error": {
    "message": "Gig with id 123 is not funded",
    "details": [
      "Expected amount: 100 DEGEN",
      "Actual amount: 0 DEGEN",
      "Token Address: 0x4ed4...",
      "Chain: base",
      "Chain id: 8453",
      "Gig wallet address: 0x1234..."
    ]
  }
}

Already Started (400)

{
  "error": "Gig is already live"
}

Not Found (404)

{
  "error": "Gig with id 123 not found"
}

In Progress (409)

{
  "error": "Gig with id 123 is currently being processed"
}

Important Notes

Pre-start Checks

• Gig must exist and not be started

• Wallet must have exact required funds

• Uses Redis lock to prevent concurrent starts

Post-start Effects

• Cannot modify gig after starting

• Records gig transaction

• Marks gig as production

Automatic Adjustments

• If start_time has passed, updates to current time

• End time adjusts accordingly