API Tester

No Auth

No authentication

API Key

Header or query

Bearer

Simple token

Basic

User & password

JWT Bearer

JWT token

Digest

Digest auth

OAuth 1.0

OAuth 1.0

OAuth 2.0

OAuth 2.0

Waiting... Time: -- Size: --
0 / 0

Send a request to view the full response body here.

Why SEO teams and backend engineers trust the ApiUji tester

The interface mirrors the workflow we use internally for production releases: plan the call, document the headers, replay it with identical auth, and store the audit trail. Because every request is executed with SSL validation, rate-limited throttles, and header hardening, you can validate live endpoints for clients or staging clusters without weakening your security posture. Add JWT claims, signed OAuth 1.0 parameters, or digest headers, then archive the response body to compare regressions before you ship.

Real-world workflows

  • Snapshot a complete request/response to share with QA.
  • Chain GraphQL queries with variables for schema smoke tests.
  • Validate webhook payloads by replaying the exact headers clients send.

SEO-focused benefits

  • Quickly confirm headers (cache, canonical, hreflang) returned by any crawlable URL.
  • Diagnose redirect chains or mixed-content warnings without leaving the browser.
  • Document response times to prove Core Web Vitals optimisations to stakeholders.

Field guide for reliable API testing

  1. Model the request first. Decide which params are query strings vs. JSON body and capture that structure in the Params and Body tabs before you ever hit Send.
  2. Use separate auth profiles. Save different API keys, JWT payloads, or OAuth signatures per project to avoid copying secrets between clients.
  3. Compare responses. Use the copy buttons to paste the exact payload into your Git issues or analytics dashboards so teammates see what search bots or mobile apps receive.
  4. Respect rate limits. ApiUji enforces our own throttles to keep the service responsive, but you should still mirror the production cadence of the API you are testing.

Need to share a reproducible bug report? Export your configuration as JSON, attach it to a ticket, and anyone on your team can import the same call, right down to multipart payloads and binary files.