Ping
The ping command simply pings the server and, on success, gets a "pong" back.
See also the Swagger specification.
See also the Swagger specification.
Ping can be used either manually or by code to check for service availability and response time.
The command passes through all interceptors (authentication, load balancing etc.) to a target server that actually executes nameapi requests. All standard behavior applies including request prioritization and request limits per contract. The only difference is that the minimal response time used on free accounts is not applied.
The command passes through all interceptors (authentication, load balancing etc.) to a target server that actually executes nameapi requests. All standard behavior applies including request prioritization and request limits per contract. The only difference is that the minimal response time used on free accounts is not applied.
GET
We have integrated Swagger directly into our API.
Visit https://api.nameapi.org/rest/swagger-ui/.
Visit https://api.nameapi.org/rest/swagger-ui/.
Input
The api-key also known as user-id. Authentication and accounting is performed on the server for this key.
Example: "32d21gc5071d7463ef6064c07ea98cb2-user1"
Example: "32d21gc5071d7463ef6064c07ea98cb2-user1"
Output
- pong