API Endpoints

The BeInfi API is organized around REST principles. All endpoints accept and return JSON, use standard HTTP methods, and require Bearer token authentication.

Base URL: https://api.beinfi.com/v1

Payments

Method	Endpoint	Description
POST	/payment-links	Create a new payment link
GET	/payment-links	List all payment links
GET	/payment-links/:id	Get a specific payment link
DELETE	/payment-links/:id	Deactivate a payment link
GET	/payments	List all payments
GET	/payments/:id	Get payment details
POST	/payments/:id/refund	Refund a payment

Marketplace

Method	Endpoint	Description
POST	/listings	Create a new listing
GET	/listings	List your listings
GET	/listings/:id	Get listing details
PUT	/listings/:id	Update a listing
DELETE	/listings/:id	Remove a listing
POST	/listings/:id/publish	Publish a draft listing

Link-in-Bio

Method	Endpoint	Description
GET	/bio	Get your link-in-bio page
PUT	/bio	Update your link-in-bio page
POST	/bio/links	Add a link to your bio page
PUT	/bio/links/:id	Update a bio link
DELETE	/bio/links/:id	Remove a bio link

AI Tools

Method	Endpoint	Description
POST	/ai/generate-description	Generate a product description
POST	/ai/generate-caption	Generate a social media caption
POST	/ai/build-page	Generate a page layout

Account

Method	Endpoint	Description
GET	/me	Get current account info
PUT	/me	Update account details
GET	/me/api-keys	List your API keys
POST	/me/api-keys	Create a new API key
DELETE	/me/api-keys/:id	Revoke an API key

Webhooks

Method	Endpoint	Description
GET	/webhooks	List webhook endpoints
POST	/webhooks	Register a new webhook endpoint
PUT	/webhooks/:id	Update a webhook endpoint
DELETE	/webhooks/:id	Remove a webhook endpoint
GET	/webhooks/:id/deliveries	List delivery attempts

Pagination

List endpoints support cursor-based pagination:

curl "https://api.beinfi.com/v1/payments?limit=20&cursor=pay_abc123" \
  -H "Authorization: Bearer YOUR_API_KEY"

Parameter	Description
limit	Number of items per page (default 20, max 100)
cursor	ID of the last item from the previous page

The response includes a has_more boolean and a next_cursor field when additional pages are available.

Error format

All errors follow a consistent format:

{
  "error": "not_found",
  "message": "The requested resource does not exist.",
  "status": 404
}