Inspector
BlogTry for free
  • Concepts
    • Introduction
    • Metrics
    • Notification Channels
      • Email
      • Slack
      • Telegram
      • Microsoft Teams
      • Google Chat
      • Webhook
      • Discord
      • Pushover
      • PagerDuty
      • Twilio - SMS
    • Filtering Syntax
    • Alerts
    • Grouping Patterns
    • Custom Segments
    • Billing
    • AI Bug Fixer
  • Security and access
    • Access control
    • Two-factor authentication
    • Connected Devices
  • SDK
    • PHP
      • Installation & Set Up
      • Custom Segments
      • Exceptions Monitoring
      • Configuration
    • Laravel / Lumen
      • Upgrade Guide
      • Installation & Set-up
      • Http Requests Monitoring
      • Configuration
      • Exception Monitoring
      • Laravel Vapor
      • Laravel Octane
      • Laravel Nova Tool
      • Group by service name
    • Symfony
      • Installation
      • Configuration
      • Exception Monitoring
    • CodeIgniter
      • Installation
      • Configuration
      • Exception Monitoring
    • Drupal
    • Spring Boot
    • Slim
    • NodeJS
      • Configurations
      • Custom Segments
      • Exception monitoring
      • Autowiring
    • ExpressJs
    • Fastify
    • Python
    • Django
      • Installation & Set Up
      • Custom Segments
      • Error Monitoring
  • REST API
    • Authentication
    • Apps
    • Platforms
    • Transactions
    • Segments
    • Analytics
Powered by GitBook
On this page
  • Base Endpoint
  • Include the key
  • Recommended Headers
  • Error codes
  1. REST API

Authentication

PreviousError MonitoringNextApps

Last updated 9 months ago

Base Endpoint

Inspector APIs are hosted on the following base URI:

https://app.inspector.dev/api

Include the key

In order to use the API you should authenticate your request by including your API key as a bearer token value in the request's headers:

Authorization: Bearer API_KEY_HERE

If you don't have an API key, you can create a new one in just a few clicks:

Recommended Headers

Make sure you have the following content type headers set on every request:

Accept: application/json 
Content-Type: application/json

Error codes

Inspector uses conventional HTTP response codes to indicate the success or failure of an API request. The table below contains a summary of the typical response codes:

Code

Description

200

Everything is ok.

401

No valid API Key was given.

404

The request resource could not be found.

422

The payload has missing required parameters or invalid data was given.

429

Too many attempts.

500

Request failed due to an internal error in Inspector.

https://app.inspector.dev/account/api