commercegov / commerce.gov-api Goto Github PK

Reported by Stuart Ridgway at Trade.gov (@pyramiddig).

The query filter for fields defaults to exact match and doesn't allow for keyword (contains) search filtering. This is a limitation of the Drupal module used to build the API, but has been updated to provide the missing operators. Additionally, the API documentation on Commerce.gov had a non-working example.

• Update API documentation to include working example of query filter usage and explain current operator limitations.
• Update Restful module to more recent version to support additional field query operators.

The link to the Query Parameter reference does not work in Firefox or Safari.
https://www.commerce.gov/data-and-reports/developer-resources/commercegov-api#field_reference

Hi!
I'm trying to use your API (to retrieve the speeches from all Secretaries of Commerce since January 2009), but it does not seem to take into account any of the parameters I enter... All links give me exactly the same results, whatever the parameters used.

For instance, all three links below produce exactly the same results:
https://api.commerce.gov/api/news/?api_key=MYKEY
https://api.commerce.gov/api/news/?api_key=MYKEY&page[offset]=50&page[limit]=50
https://api.commerce.gov/api/news/?api_key=MYKEY&page[offset]=100&page[limit]=50

Same when I try to filter by speaker or news_type.

Do you know how I could effectively enter parameters? Would you mind sharing an example of a correct use of such filters (if I'm doing it wrong) please?

Many thanks!

https://api.commece.gov/api/blogs <--- this link has a typo. Should be https://api.commerce.gov/api/blogs

I have an app using this API for a couple of months. Today, I found that the API does not work for some reasons. For example: I tried to run request on https://api.commerce.gov/api/blogs?api_key=DEMO_KEY, where DEMO_KEY is my key, and I got the following errors:

{
    "jsonapi": {
        "version": "1.0",
        "meta": {
            "links": {
                "self": {
                    "href": "http://jsonapi.org/format/1.0/"
                }
            }
        }
    },
    "errors": [
        {
            "title": "Bad Request",
            "status": "400",
            "detail": "The following query parameters violate the JSON:API spec: 'q'.",
            "links": {
                "via": {
                    "href": "https://www.commerce.gov/api/blogs?q=%2Fapi%2Fblogs"
                },
                "info": {
                    "href": "http://jsonapi.org/format/#query-parameters"
                }
            }
        }
    ]
}

Do you have any idea what happened? Thank you.

When calling the api.commerce.gov APIs, they all now return a 404 error code with the HTML for the 404 page for the main commerce.gov site.

For example, visit: https://api.commerce.gov/api/news?api_key=XXXX

Seems like you should use an API monitoring service for production APIs. I humbly suggest APImetrics (I may be slightly biased there, I'm a co-founder of that company).

Greetings,
Could you please provide API for below fields under news for the Current Week always. We have registered for API Key.

News Type : Fact Sheet
Issues:
Economicindicators , Export and investment promotion, Manufacturing, Trade enforcement

Here the API that we constructed and we are not sure of its giving required news.

https://api.commerce.gov/api/news?news_type=fact-sheets&issues[]=59&issues[]=58&issues[]=48&issues[]=52&post_date_formatted=2022-12-05&api_key=API_KEY