Partner API Technical Overview

Modified on Thu, 29 Jan at 3:11 AM

This article is intended for developers implementing the Partner API.

Authentication

All Partner API requests must include a valid Bearer token for authentication.

Authorization: Bearer YOUR_PARTNER_TOKEN

API Base URLs

Production: https://api.spurropen.com
Testing: https://sandbox.api.spurropen.com

Request Format

All requests to the Partner API must follow these standards:

HTTP Methods: GET or POST, depending on the endpoint
Headers:
- Content-Type: application/json
- Authorization: Bearer {token}
Request Body: JSON format (POST requests only)

Endpoint Summary

Method	Endpoint	Purpose
GET	/events	List available events
GET	/events/{id}	Retrieve event details
GET	/events/{id}/tickets	List ticket options for an event
GET	/events/{id}/tickets/{id}	Retrieve ticket details
POST	/orders/preview	Preview order totals
POST	/orders	Create an order and reserve inventory
POST	/orders/{id}/confirm	Confirm payment and complete the order

Response Codes

The Partner API uses standard HTTP response codes to indicate request status.

200 OK: Request completed successfully
201 Created: Resource created successfully
400 Bad Request: Invalid request format or data
401 Unauthorized: Missing or invalid authentication token
403 Forbidden: Insufficient permissions
404 Not Found: Requested resource does not exist
409 Conflict: Duplicate or conflicting request
422 Unprocessable Entity: Business rule validation error
500 Server Error: Unexpected error, contact support if persistent

Documentation and API Reference

For detailed technical documentation, including request parameters, response schemas, example payloads, and authentication details, refer to the official API documentation.

API Documentation: https://api.spurropen.com/docs

Use this support site for implementation guidance and troubleshooting, and the API documentation for full endpoint specifications and technical reference.