Why does the request work in curl but not here?

The target may not allow cross-origin browser requests. A network error can also come from DNS, TLS, connectivity, or an unavailable endpoint.

Are authorization tokens saved?

No. Request URLs, headers, authorization values, and bodies remain in page memory and disappear when you reload or leave the page.

Which cURL options can I import?

The importer supports common URL, method, header, data, Basic Auth, and Bearer header options. It rejects unsupported flags and never executes shell commands.

Developer

API Client

Build and send REST API requests from your browser, inspect status, headers, and bodies, then generate reusable request code.

Direct browser request. Data is sent only to the target endpoint.

ParameterValue

TimeoutsecondsResponse limit: 2 MB

No response yet

Configure the request and select Send. Browser CORS rules apply.

Requests are sent directly from your browser to the target endpoint. CORS rules apply.

Import cURL

cURL command

Supports URL, method, headers, data, Basic Auth, and Bearer headers. Shell commands are parsed as text and never executed.

Generate code

Generated request

Enter an endpoint URL.

How to use it

Choose an HTTP method and enter an endpoint that permits browser requests.
Add query parameters, headers, authorization, or a request body.
Send the request, inspect the response, and copy or generate reusable code.

Example

Input

GET https://jsonplaceholder.typicode.com/posts?userId=1

Output

HTTP status, response time, headers, and a formatted JSON body.

Browser mode

Requests travel directly from your browser to the endpoint you enter. Naminc Tech Tools does not receive the URL, headers, credentials, request body, or response.

How CORS affects requests

Browsers enforce Cross-Origin Resource Sharing rules. The target server must allow your origin and requested headers, or the browser may block access to the response.

Why curl may still work

Command-line clients do not enforce browser CORS rules. A request can succeed in curl and fail here because of CORS, although DNS, TLS, connectivity, or endpoint availability can also cause network failures.

Protect API credentials

Use tokens only on a trusted device, confirm the destination URL before sending, and clear the workspace when finished. Reloading the page removes request data from memory.

Common questions

Does Naminc Tech Tools receive my API request?: No. Browser mode uses Fetch API to connect directly from your browser to the target endpoint. There is no Naminc proxy in this tool.
Why does the request work in curl but not here?: The target may not allow cross-origin browser requests. A network error can also come from DNS, TLS, connectivity, or an unavailable endpoint.
Are authorization tokens saved?: No. Request URLs, headers, authorization values, and bodies remain in page memory and disappear when you reload or leave the page.
Which cURL options can I import?: The importer supports common URL, method, header, data, Basic Auth, and Bearer header options. It rejects unsupported flags and never executes shell commands.