Generate API Docs
Forward your API code, endpoint list, or spec file; get structured documentation with parameters, responses, auth, and usage examples.
These are the three payment endpoints our checkout team built last quarter. The mobile team needs to integrate but there are no docs. Can you generate documentation from this?
---------- Forwarded message ----------
On Monday, March 9, 2026, Sam Reeves sam.reeves@pinegrovetech.io wrote:
Here are the payment endpoints:
POST /api/v2/payments
Creates a new payment intent. Requires auth header with Bearer token.
Body: { amount: integer (cents), currency: string (ISO 4217), customer_id: string, payment_method: string, metadata: object (optional) }
Returns: { id: string, status: pending|processing|completed|failed, amount: integer, created_at: timestamp }
Errors: 400 invalid params, 401 unauthorized, 422 insufficient funds
GET /api/v2/payments/:id
Retrieves payment by ID. Same auth.
Returns full payment object with additional fields: updated_at, failure_reason (if failed), receipt_url (if completed)
POST /api/v2/payments/:id/refund
Initiates full or partial refund.
Body: { amount: integer (optional, defaults to full), reason: string (optional) }
Returns: { refund_id: string, payment_id: string, amount: integer, status: pending|completed }
Errors: 400 already refunded, 404 payment not found
Auth is JWT tokens from our /auth/token endpoint. Tokens expire after 1 hour. Rate limit is 100 req/min per API key.
Sam
---------- Forwarded message ----------
On Monday, March 9, 2026, Sam Reeves sam.reeves@pinegrovetech.io wrote:
Here are the payment endpoints:
POST /api/v2/payments
Creates a new payment intent. Requires auth header with Bearer token.
Body: { amount: integer (cents), currency: string (ISO 4217), customer_id: string, payment_method: string, metadata: object (optional) }
Returns: { id: string, status: pending|processing|completed|failed, amount: integer, created_at: timestamp }
Errors: 400 invalid params, 401 unauthorized, 422 insufficient funds
GET /api/v2/payments/:id
Retrieves payment by ID. Same auth.
Returns full payment object with additional fields: updated_at, failure_reason (if failed), receipt_url (if completed)
POST /api/v2/payments/:id/refund
Initiates full or partial refund.
Body: { amount: integer (optional, defaults to full), reason: string (optional) }
Returns: { refund_id: string, payment_id: string, amount: integer, status: pending|completed }
Errors: 400 already refunded, 404 payment not found
Auth is JWT tokens from our /auth/token endpoint. Tokens expire after 1 hour. Rate limit is 100 req/min per API key.
Sam
What is via.email?
AI agents that each lives at an email address. Just send an email to get work done. No apps. No downloads.
How to use?
Send or forward emails to agents and get results replied. Try it without registrations. Join to get free credits.
Is it safe?
Absolutely, your emails will be encrypted, deleted after processing, and never be used to train AI models.
More power?
Upgrade to get more credits, add email attachments, create custom agents, and access advanced features.