Inshorts News Getting Started: Account, Keys, First Call (2026)

Getting started overview

Integrating the Inshorts News API into an application involves a series of steps focused on authentication and request construction. This guide provides a rapid path to making a first successful API call, covering account setup, credential retrieval, and basic request execution. Developers can access summarized news articles, often with a focus on the Indian market, for display within their platforms.

The Inshorts News API generally follows REST principles, utilizing standard HTTP methods for communication. Authentication typically relies on API keys, which are passed with each request to verify the client's identity and authorization to access the data. Understanding the structure of a RESTful API, including resource identification and data formats like JSON, is foundational for a successful integration REST API principles.

Before making any API calls, it is necessary to establish an account with Inshorts News. This process secures access and provides the unique credentials required for interaction. Following account setup, the focus shifts to obtaining and correctly utilizing these credentials in a programmatic context.

Summary of initial steps:

1. Create an Inshorts News account.
2. Obtain API access keys/tokens.
3. Construct and execute an authenticated API request.
4. Process the JSON response.

Create an account and get keys

Accessing the Inshorts News API requires an active account with the service. While Inshorts News primarily offers an application for news consumption, developers seeking API access for integration purposes typically engage through a dedicated process for enterprise or partnership inquiries, as indicated by its custom enterprise pricing model Inshorts News homepage. Direct sign-up for a public-facing developer portal and instant API key generation, common with other public APIs, is not explicitly detailed on their primary consumer-facing website.

To initiate the process of obtaining API keys, developers should:

1. Visit the Inshorts News official website: Navigate to Inshorts News.
2. Locate partnership or enterprise contact information: Look for sections like "Contact Us," "Partnerships," "Business," or similar links that lead to inquiries for commercial or API integration. Given the custom enterprise pricing, direct contact is generally required.
3. Submit an inquiry: Provide details about your project, expected usage, and technical requirements. This allows the Inshorts team to assess your needs and provide relevant access information and pricing.
4. Follow up: Await communication from Inshorts News. They will typically guide you through the process of setting up an enterprise account and issuing the necessary API keys or tokens. These credentials are unique to your account and authorize your application to make requests to their API.

Once provided, your API key or token will be a string of characters that must be included with your API requests. The specific method for including the key (e.g., as a query parameter, HTTP header, or part of a request body) will be detailed in the documentation provided upon successful account creation and key issuance. Adhering to secure practices for handling API keys, such as not embedding them directly in client-side code and using environment variables or secret management services, is recommended Google Cloud API key best practices.

Your first request

After obtaining your API key from Inshorts News, the next step is to construct and execute your first API call. This process demonstrates whether your authentication mechanism is correctly configured and confirms connectivity to the Inshorts News API endpoint. The exact API endpoint and parameters will be provided by Inshorts News upon successful account setup and API key issuance, but the general principles remain consistent for RESTful APIs.

Assuming Inshorts News provides an endpoint for fetching recent news, a common pattern involves an HTTP GET request to a specific URL, with authentication details included. For demonstration, let's use a hypothetical endpoint and key usage pattern.

Example Request Structure (Hypothetical)

GET /api/v1/news HTTP/1.1
Host: api.inshorts.com
Authorization: Bearer YOUR_API_KEY
Accept: application/json

In this hypothetical example:

• GET /api/v1/news: Specifies the HTTP method and the resource path to retrieve news articles.
• Host: api.inshorts.com: The domain of the Inshorts News API.
• Authorization: Bearer YOUR_API_KEY: This header carries your API key. Replace YOUR_API_KEY with the actual key provided by Inshorts News. The "Bearer" scheme is a common pattern for token-based authentication RFC 6750 for Bearer Token Usage.
• Accept: application/json: Indicates that the client prefers a JSON response.

Executing the Request with cURL

cURL is a command-line tool and library for transferring data with URLs, widely used for testing API endpoints. To make a request:

curl -X GET \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json" \
  "https://api.inshorts.com/api/v1/news"

Remember to replace YOUR_API_KEY with your assigned key and verify the correct API endpoint with Inshorts News's provided documentation.

Expected Response

A successful request (HTTP status code 200 OK) will typically return a JSON object containing an array of news articles. Each article object would likely include fields such as title, summary, source, and a URL. For example (simplified hypothetical):

{
  "status": "success",
  "data": [
    {
      "id": "12345",
      "title": "Example News Headline",
      "summary": "This is a brief summary of an example news article from Inshorts.",
      "source": "Example Source",
      "url": "https://www.inshorts.com/news/example-headline",
      "category": "national"
    },
    // ... more news articles
  ]
}

If you receive a different status code (e.g., 401 Unauthorized, 403 Forbidden, 404 Not Found), consult the Troubleshooting the first call section.

Common next steps

Once you've successfully made your first API call to Inshorts News and received a valid response, you can proceed with further integration and development. These steps often involve refining data retrieval, handling responses gracefully, and integrating the news content into your application's user interface or backend processes.

Step-by-step next actions:

1. Explore additional endpoints and parameters: Review the Inshorts News API documentation (provided upon successful key issuance) for available endpoints beyond the basic news feed. This might include categories, search functionality, or specific article retrieval. Experiment with query parameters to filter or paginate results, such as category=politics or count=10.

2. Implement robust error handling: Design your application to gracefully handle various API responses, including different HTTP status codes (e.g., 4xx client errors, 5xx server errors) and structured error messages within the JSON response. This prevents application crashes and provides better user feedback.

3. Integrate with your application's frontend/backend:

   • Frontend: Parse the JSON response and display the news articles in your application's user interface. Consider how summaries, images (if provided), and source links will be presented. Ensure responsive design for various devices.
   • Backend: If your application requires server-side processing, integrate the API calls into your backend logic. This could involve caching news, performing further analysis, or distributing news to multiple clients.

4. Manage API request limits: Be aware of any rate limits imposed by Inshorts News to prevent abuse. Implement mechanisms like exponential backoff for retries to avoid exceeding these limits AWS API Error Retries and Exponential Backoff. Understanding and respecting rate limits is crucial for maintaining consistent access.

5. Secure your API key: Reiterate the importance of keeping your API key secure. Do not expose it in client-side code. Use environment variables, secret management services, or server-side proxies to make API calls securely.

6. Consider data freshness and caching: Determine how frequently you need to fetch new content and implement caching strategies to reduce the number of API calls and improve application performance. Respect any caching headers (e.g., Cache-Control) provided in the API responses.

7. Monitor API usage: If Inshorts News provides a dashboard or logs, regularly monitor your API usage to ensure it aligns with your expectations and to identify any potential issues or unauthorized access.

Troubleshooting the first call

Encountering issues during your initial API call is common. Here's a quick reference table and some common problems with their solutions:

Common Issues and Solutions:

1. HTTP 401 Unauthorized / 403 Forbidden

• Problem: Your API key is missing, incorrect, expired, or doesn't have the necessary permissions.
• Solution:
  • Double-check that you've correctly copied and pasted your API key.
  • Ensure the API key is included in the correct header or query parameter as specified by Inshorts News (e.g., Authorization: Bearer YOUR_API_KEY).
  • Verify your account status with Inshorts News. Your access might be pending or revoked.

2. HTTP 404 Not Found

• Problem: The API endpoint URL is incorrect or the resource you're trying to access does not exist.
• Solution:
  • Compare the endpoint URL in your request precisely with the one provided in Inshorts News's documentation. Pay attention to case sensitivity, slashes, and any versioning (e.g., /v1/).
  • Ensure the API endpoint is active and not deprecated.

3. HTTP 429 Too Many Requests

• Problem: You have exceeded the allocated rate limit for your API key.
• Solution:
  • Wait for the rate limit window to reset before making further requests.
  • Implement client-side rate limiting or exponential backoff in your application to prevent this in the future.
  • Review Inshorts News's documentation for specific rate limit policies.

4. Network Issues / Connection Timeout

• Problem: Your application cannot establish a connection to the Inshorts News API server.
• Solution:
  • Check your internet connection.
  • Verify that no firewall or proxy settings are blocking outgoing requests to api.inshorts.com.
  • Confirm the Inshorts News API servers are operational (though an official status page might not be publicly available given the enterprise model).

5. Invalid JSON / Malformed Response

• Problem: The API returns a response that isn't valid JSON or doesn't match the expected structure.
• Solution:
  • Examine the raw response body. Sometimes, error messages are returned as HTML or plain text, indicating an underlying problem.
  • Ensure your request included the Accept: application/json header if necessary to explicitly request JSON.
  • Compare the actual response structure to the expected structure in Inshorts News's documentation.

For persistent issues, refer to the specific documentation provided by Inshorts News upon API key issuance. If unresolved, contacting Inshorts News support directly via the channels provided during your enterprise engagement is the next appropriate step.