Send REST and GraphQL requests, run checks, inspect JSON responses, organize collections, and switch environments in a free, browser-based API testing workspace.
◈Private, local workspace. Saved in this browser, not synced. Clearing site data may erase it — export backups regularly.
Organize request
Stream events
No events yet.
Keeps the newest 200 entries within 2 MiB. Message limit: 1 MiB. Binary WebSocket frames show a bounded hex preview. Events stay in memory; copied or downloaded events may contain sensitive response or outgoing message data.
ResponseReady
Preview limited to 1 MiB of text. Copy or Download keeps the full response (up to 10 MiB).
Send a request to inspect the response.
No checks run yet.
A practical workflow
Prepare a request to an endpoint you are authorized to use, inspect headers and body, then save the request with the intended environment.
Read the scope alongside the result
Sending contacts the selected endpoint. Browser permissions do not bypass CORS, and saved/exported workspace material can contain sensitive values. Local storage is not cloud sync.
Open Collection runner & imports to run saved REST/GraphQL requests in order with environment overrides, cancellation, iterations and status/timing reports. Structured JSON Pointer and header checks run on individual requests and collection runs. Preview Postman collections/environments or OpenAPI JSON before adding them to your workspace. Imported scripts are excluded; unsupported features appear in the compatibility report.
WebSocket, SSE and GraphQL subscriptions
Choose WebSocket for a text-message client with binary frame previews, or Server-sent events for an authenticated HTTP GET stream. GraphQL subscriptions support graphql-transport-ws and GraphQL SSE distinct connections. Connect, disconnect, optionally reconnect, filter events and download the visible log. Native browser WebSocket cannot set custom handshake headers. SSE uses streaming fetch so it can use the existing authorization settings. Connections and message logs are never restored automatically.
REST and GraphQL API testing
Choose GraphQL in Request type to send queries and mutations with JSON variables and an operation selector. Use POST for queries, mutations and multipart Upload files, or GET for queries. Load or import a schema for searchable type documentation and field validation. Authentication, environments, collections, history and cURL export work with both request types. Use the Checks view to distinguish GraphQL errors from HTTP errors. Transport follows the GraphQL HTTP guidance.
Free online REST API tester and HTTP client
PixelOkay API Tester is a browser-based tool for checking REST endpoints, experimenting with HTTP requests and debugging API responses. Use it to send GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS requests, set custom headers and query parameters, and examine response bodies, status codes, timing and returned headers. No installation or account is required.
Organize frequent endpoints into collections, create development and staging environments, reuse variable placeholders, and import or export a local workspace as JSON. You can also copy a request as cURL or import a basic cURL command. API requests run directly from your browser, so an endpoint must allow cross-origin access (CORS) for browser testing.
Test localhost and private-network APIs
Enter http://localhost:3000, http://127.0.0.1:5000, or a LAN endpoint such as http://192.168.1.10:8080. When a local address is detected, the workspace displays setup instructions and a copyable Express CORS example. Supported browsers may ask for Local Network Access permission when PixelOkay is served over HTTPS. Your local API still needs to allow this website origin through CORS. This tool does not run a proxy and cannot bypass network or browser restrictions.
How to test an API
Enter an HTTP or HTTPS URL and choose a request method.
Add query parameters, headers, authentication or a JSON body as needed.
Click Send to inspect the response status, timing, headers and body.
Save reusable requests in collections, switch environments or export your workspace.
Browser security and privacy
Requests are sent directly from your browser to the target server. Drafts, collections, history and environments are automatically saved in browser localStorage where available; this is not a guaranteed backup and is isolated per website origin. Export JSON regularly. Cross-origin requests require permission from that server through CORS. PixelOkay does not proxy requests or receive your API credentials through this app. Saved requests and history stay in your browser; avoid putting secrets in URLs, headers or bodies you intend to save. Browser storage can be cleared by your browser or by you.
When to use an API testing tool
Verify a REST endpoint before connecting a front end, check an API's response shape and headers, experiment with authenticated requests, and compare development and staging endpoints using environment variables. For QA and debugging, save reproducible requests in collections and use the optional expected-status check to catch unexpected HTTP status codes.
Supported workflows
GET, POST, PUT, PATCH, DELETE, HEAD and OPTIONS requests; bearer, basic and API-key authentication; JSON, text and URL-encoded bodies; query parameters; local collections, environments and JSON backup.
When to use this tool
Debug an HTTP endpoint, compare response headers and body, or organize reusable requests in local collections. The browser sends requests directly to the endpoint and cannot bypass CORS or local-network permissions.
A request workflow
Choose GET and a test endpoint you control, add query parameters, and inspect the status, headers and JSON response. Save a reusable request in a collection or export a workspace backup. Test POST, PATCH and DELETE with sample data because a server can process writes before cancellation.
Frequently asked questions
Is PixelOkay API Tester free?
Yes. It runs in your browser without an account or paid plan. API servers may have their own rate limits, authentication requirements, or charges.
Can I test a local API on localhost?
Yes, if the API is running, CORS allows the PixelOkay page origin, and your browser permits access. In browsers supporting Local Network Access, grant loopback or local-network permission if asked. The workspace provides a tailored guide for localhost and LAN URLs.
Does my workspace persist after I close the browser?
Normally yes, in this browser and on this site. Browser storage can be deleted by privacy modes, browser cleanup or storage policies. Export your workspace regularly. The main-site and subdomain versions have separate storage.
Why does a request work in Postman but fail here?
Browsers enforce CORS, unlike native API clients. The destination API must permit your origin and requested headers. This product does not bypass that protection.
Can I use environment variables?
Yes. Create environments in Settings and use variables as double-braced placeholders in URLs, headers and bodies.
Does cancelling undo a request?
No. Cancellation stops the browser from waiting, but a server might already have processed a write.
Are collections synchronized?
No. Data is local to this browser. Export JSON to back it up or transfer it.
