Choose an API product or a service
Choose according to whether the customer buys ongoing API access or a one-time delivery. Link the two when they belong together.
On this page
Repeated calls: an API product
Use this for a public HTTPS API, such as document processing, data lookups, or report generation. You operate the API and pay upstream costs. Customers receive plan-based endpoint access, usage allowances, and their own key.
Prepare your OpenAPI document, real origin, and plans, then follow the first API tutorial. Invokora does not run or edit the implementation behind your API.
A defined piece of work: a service
Use this for installation, configuration, migration, debugging, or custom work. Sell a fixed price when the deliverables are clear, or use a quote to agree scope first.
After payment, customers submit formal requirements. You communicate, deliver, and obtain acceptance in the order. Ongoing maintenance can be purchased separately after acceptance.
Sell an API with related services
- When creating a service, select an API product from the same merchant as its related source.
- Check the related-service entry on the API product page and in the buyer workspace.
- State whether the service requires the buyer to purchase an API plan separately. Linking does not bundle prices, grant API access, or merge orders.