YetAnotherAPI Documentation
Signup for APIGo to main websiteContact Support
  • API Documentation
    • YetAnotherAPI Overview
    • Authentication
  • Integrations
    • Pabbly-Connect
  • Document parser
    • PDF Parser
    • Doc Parser
    • PNG & JPG Parser
    • TXT Parser
    • Parser Processing Status
  • Web Scrapper [deprecated]
    • Basic Web Scraper
    • LLM Web Scraper
    • Scrapper Processing Status
  • Web Scraper
    • Basic Web Scraper
    • Webpage links Scrapper
    • Metadata Scrapper
    • Webhook Notification
    • Status Check
  • LLM Web Scraper
    • Basic Text
    • Structured JSON
    • Best Practices
    • Use Cases
    • Status Check
  • UChat Webhook System
Powered by GitBook
On this page
  • Overview
  • API Key Authentication
  • Security Best Practices
  • Error Responses
  • Support

Was this helpful?

  1. API Documentation

Authentication

Overview

All requests to YetAnotherAPI services require authentication. This document outlines the authentication process and best practices for securing your API access.

API Key Authentication

Obtaining an API Key

  1. Sign up for an account at YetAnotherAPI platform

  2. Navigate to the API Keys section in your dashboard

  3. Generate a new API key for your application

Using Your API Key

Include your API key in the request header for all API calls:

x-api-key: YOUR_API_KEY

Example Request

curl --location 'https://api.yetanotherapi.com/v1/endpoint' \
--header 'x-api-key: YOUR_API_KEY_HERE' \
--header 'Content-Type: application/json'

Security Best Practices

  1. Key Protection

    • Never expose your API key in client-side code

    • Don't commit API keys to version control

    • Rotate keys periodically for enhanced security

  2. Environment Management

    • Use different API keys for development and production

    • Store keys in secure environment variables

    • Implement key rotation procedures

  3. Access Control

    • Monitor API key usage regularly

    • Revoke compromised keys immediately

    • Use the minimum required permissions for each key

Error Responses

Status Code
Description
Solution

401

Invalid API key

Check if key is correct and active

403

Insufficient permissions

Verify key has required access levels

429

Rate limit exceeded

Reduce request frequency or upgrade plan

Support

If you encounter authentication issues or need assistance, contact our support team through the support portal.

PreviousYetAnotherAPI OverviewNextIntegrations

Last updated 6 months ago

Was this helpful?