Quintype provides a comprehensive set of APIs that publishers and developers can use to fetch stories, authors, collections, RSS feeds, members, and more. The easiest way to explore and test these APIs is through Swagger UI.

Where to Access Quintype APIs

You can explore all supported APIs using the Swagger interface:

Swagger UI: https://developers.quintype.com/swagger/#/

Swagger allows you to:

• View all available APIs
• Understand required parameters
• Test API requests live
• Generate sample API URLs for use in your website or app

Why Use Swagger First?

Before integrating any API into your website or app, it’s recommended to:

• Try the API in Swagger
• Validate filters and parameters
• Review the response structure
• Copy the working API request for implementation
• This avoids trial-and-error during development.

Example: Using the Advanced Search API

If you want to:

• Fetch recently published stories
• Filter stories by publish date
• Filter by section, tag, or other attributes

You should use the Advanced Search API:

Endpoint:
GET /api/v1/advanced-search

Common Use Cases

• Get stories published after a specific date
• Fetch content from a particular section
• Retrieve only published stories
• Apply multiple filters in a single request

How to Use It in Swagger

1. Open the Swagger UI
   Visit: https://developers.quintype.com/swagger/#/
2. Select the API Category
   Browse through categories such as story, advanced-search, authors, collections, or member, based on your requirement.
3. Choose an API Endpoint
   Click on the required endpoint (for example, GET /api/v1/advanced-search) to expand its details.
4. Click Try it out
   This enables the input fields so you can add parameters.
5. Add Required Parameters
   Enter values such as:
6. Publish timestamps (for example, published-after)
7. Section ID, tag, or entity filters
8. Limit and offset for pagination
9. Execute the API
   Click Execute to run the API request.
10. Review the Response
    Check the response body to verify the data returned (stories, metadata, IDs, etc.).
11. Copy the Generated API URL
    Swagger generates the full request URL. You can copy this URL and use it directly in your website or application.
12. Refine and Re-test
    Adjust parameters as needed and re-run the API until you get the desired output.

Note: Date and time values must be passed in the expected timestamp format, as shown in Swagger. 
Convert Date & Time to Epoch (Milliseconds)

API time-based filters (like published-after or published-before) require epoch time in milliseconds.

Use any Epoch Time Converter to convert your date and time into milliseconds (not seconds).

Example: Using Advanced Search with Epoch Time (Milliseconds)

Use case: Fetch stories published after December 9, 2025, 12:00 AM IST.

Step 1: Convert Date to Epoch Time (Milliseconds)

Date & Time: Dec 9, 2025, 12:00 AM IST

Converted Epoch Time (milliseconds):
1765218600000

⚠️ Note: Always use milliseconds, not seconds.

Step 2: Use the Advanced Search API in Swagger

Endpoint:

Sample Parameters:

published-after: 1765218600000

limit: 10

offset: 0

Step 3: Execute and Copy the API URL

After clicking Execute in Swagger, you’ll get a generated URL similar to:

You can directly use this URL in your application or website to fetch recently published stories.

Best Practice for API Usage

• Use Advanced Search instead of multiple basic APIs when filtering content.
• Always test filters in Swagger before implementation.
• Avoid hardcoding assumptions-validate responses first.
• Use only the required APIs instead of calling multiple endpoints unnecessarily.

Important Note

At the moment, not all API usage examples are documented in detail on the help site. Swagger should be treated as the primary reference for:

• Supported APIs
• Parameters
• Request and response formats

If you are unsure which API fits your use case, testing it in Swagger is the fastest way to confirm.