Skip to main content

Test the HTTPBIN Service and Route

Now you created the HTTPBIN service and a JSON route for it. Let's send a request to verify if it's working.

curl -H 'Host:' -v

We set the host header to and the request path to /json. And you have an APISIX instance listening on as per the guide. So you'll see the output below.

*   Trying
* Connected to ( port 9080 (#0)
> GET /v1/json HTTP/1.1
> Host:
> User-Agent: curl/7.76.1
> Accept: */*
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 429
< Connection: keep-alive
< X-RateLimit-Limit: 5
< X-RateLimit-Remaining: 4
< Date: Fri, 22 Apr 2022 02:20:41 GMT
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Credentials: true
< Server: APISIX/2.15.0
"slideshow": {
"author": "Yours Truly",
"date": "date of publication",
"slides": [
"title": "Wake up to WonderWidgets!",
"type": "all"
"items": [
"Why <em>WonderWidgets</em> are great",
"Who <em>buys</em> WonderWidgets"
"title": "Overview",
"type": "all"
"title": "Sample Slide Show"

As you can see, we got a JSON string from APISIX, which is the response that we want to get (from


HTTPBIN service randomly generates the JSON string data, so the data you got might differ from the data you get from this request.

Congratulations! Now that you test the HTTPBIN service and its JSON route, everything is working.


Attach the Limit Count Plugin. Logo

API Management for Modern Architectures with Edge, API Gateway, Kubernetes, and Service Mesh.


API7 Cloud

SOC2 Type IRed Herring

Copyright © APISEVEN Ltd. 2019 – 2024. Apache, Apache APISIX, APISIX, and associated open source project names are trademarks of the

Apache Software Foundation