If it's not added yet, it should be.

If it is, it should be confirmed that it's the right snippet. I worry that it may be overlapping with the SAM API or even CFPB GA code.

@nvembar

From API Best Practices:

• Make your hub findable by using a common URL: www.agency.gov/developer
• The url of www.agency.gov/developers should also work.

gsaauctions.gov/developer and gsaauctions.gov/developers should bother redirect to http://gsa.github.io/auctions_api/

The default response size (>>10MB) is very large. Suggest adding the ability to get a subset of data (e.g. pagination) with a default response size of somewhere between 50 and 200 items in the response

Possible ways to implement:

• page query parameter with an optional page_size that determines the number of responses per page
• start and limit parameter that allow arbitrary subsets of the resources of a collection (e.g. slices). similar to pages except without starting at fixed indices

for collections, also nice to put a property indicating total items in the collection and /or max number of pages.

@kishoregh - I think you should be able to get your API listed on gsa.gov/developer by following up on the GSA api listserve with a request.

Hi, I ran the raw JSON file through a JSON validator and found multiple syntax errors. I am going through them one by one and fixing, but was wondering if anyone else found the same issue + was unable to use the API for this reason? I'm a noob at making data requests from APIs, so go easy on me. :)

If/after I am done fixing the syntax errors, I can post the resulting JSON file here. The most common problem has been double quotes within double quotes. :(

I'm not sure what's up but the styling is different in a couple ways on the API Calls page.

The main one is how the sidebar works. Here's how I see it in Chrome on most pages:

But here's how it looks on /console:

I'm guessing that a link in this file to a styling resource is broken but am not sure.

@adelevie, @nvembar - any thoughts?

My call to https://api.data.gov/gsa/auctions?api_key=DEMO_KEY&format=JSON wouldn't parse as valid JSON

JSON parser gave:
Unexpected token }

Are there parameters by which a developer can query the underlying data? Those would increase the utility of the service significantly.

Once some are articulated, it'll be important to add them to the /basics page.

In November 2018, the GSA CTO and CIO directed all API programs at GSA to implement the GSA API Standards (details here). All current APIs at the agency have a deadline of Dec. 31, 2019 to do this.

This issue is to track the Auctions API's adoption of the Standards.

• Add Your API To The GSA API Directory
• Use The api.data.gov Service
• Provide Support For Versioning
• Provide Public Documentation
• Provide A Feedback Mechanism That Is Clear and Monitored
• Provide An OpenAPI Specification File

...from the repo description:

@GUI - can you share instructions or file a pull request for how we could integrate the api key signup into a page on gsa.github.io/auctions_api?

I'd then recommend adding a sidebar nav item for the api key signup page. That way developers don't leave your microsite when they get a key

I wanted to play around with the Console, but it does not seem to be showing up--I see a blank spot where the console should be. I'm using the latest version of Chrome, and also checked Safari.

Screenshot: