We send traffic to your online store from GoCollect.com, ComicList.com and soon-to-launch apps for both iOS and Android platforms.
You simply provide us with a URL that communicates your online inventory (i.e. your "feed"). Our system reaches out and grabs that feed at regular hourly intervals to keep your inventory and pricing as accurate as possible.
We're software engineering geeks. If you're not, that's 100% OK. We'll figure out a way to work with you. If the stuff below doesn't make sense, don't worry. Just get in touch with us and we'll try to figure it all out together.
We can accept your feed in any number of formats (XML, JSON, CSV, etc) and we can grab that from you via URL or FTP. If we're not already equipped to handle it, we'll get it in place on our end. All we ask is that your feed follow a particular structure.
The specifics may change slightly depending on your delivery format, but the below is a general overview of the information (and appropriate argument names) we're looking for in each of the comics you want included in our database.
|retailerComicId Optional||The retailer's internal ID of the type of comic being offered for sale. See the Meaning for retailerSaleId for more info.|
|retailerSaleId Required||The retailer's internal ID of the specific instance of the coming being offered for sale. As an example, let's assume the retailer is selling 2 different copies of The Incredible Hulk #181. One is professionally graded as a 9.8, while the other is professionally graded as a 8.5. Both sales should have a different retailerSaleId in order to uniquely identify them. However, both of those sales should share the same retailerComicId in order to associate them.|
This identifies the type of primary key that will be used to identify the comic in the GoCollect database. One of the following values must be used:
|comicIdKey Required||The value of primary key as identified by the comicIdType.|
|price Required||The current asking price or next bid price (USD) for the comic being sold.|
|inventory Optional||The current in-stock inventory for the comic being sold. While not required, this field is strongly recommended.|
|saleTitle Optional||Any title assigned to the sale listing. Ex. The Incredible Hulk #181 signed by Stan Lee|
The sale format of the comic being offered. It must be one of the following:
|bidCount Optionally Required||This value is required Auction format listings. It represents the current number of bids that have already been placed on the comic.|
|auctionEndTime Optionally Required||This value is required Auction format listings. It represents the time the auction ends. It must be in ISO 8601, "Complete date plus hours and minutes" format: YYYY-MM-DDThh:mmTZD (eg 1997-07-16T19:20+01:00).|
|url Required||This is the link the customer will be directed to when they click to learn more about the comic you're selling.|
|imageUrl Optional||This is a link to a thumbnail image of the comic you're offering for sale.|
|condition Optional||Represents the numerical condition of the comic being sold. If present, it must be one of the following: 10.0, 9.9, 9.8, 9.6, 9.4, 9.2, 9.0, 8.5, 8.0, 7.5, 7.0, 6.5, 6.0, 5.5, 5.0, 4.5, 4.0, 3.5, 3.0, 2.5, 2.0, 1.8, 1.5, 1.0, 0.5, 0.3|
If the comic being offered for sale has been professionally graded, we suggest using one of the following values. Professionally graded comics will take precedence in our search results.8 = CBCS Authentic Sig - Yellow
15 = CBCS Authentic Sig - Yellow (Restored)
7 = CBCS Certified - Blue
16 = CBCS Certified - Blue (Conserved)
12 = CBCS Certified - Blue (Restored)
11 = CBCS Verified - Red
18 = CBCS Verified - Red (Conserved)
14 = CBCS Verified - Red (Restored)
13 = CGC Conserved
6 = CGC Modern
3 = CGC Qualified
4 = CGC Restored
2 = CGC Signature Series
17 = CGC Signature Series Qualified
5 = CGC Signature Series Restored
1 = CGC Universal
10 = PGX Signature
9 = PGX Standard
|graderKey Optional||This is the identifier of the graded comic within the grader's database. For instance, CGC refers to this as the Certification Number, while CBCS refers to this as the Barcode Number.|
The JSON feed format should be a single object that contains one or more child objects. Each child object is referenced below.
NOTE: Please don't use "JSON padding" as this will be fetched server-to-server, outside of a user's browser.
|retailer Required Object||
The following fields are available for this object:
|comics Required Array||This is an array objects, where each instance represents the comics that are to be fed into GoCollect. The keys for each object are the same as those detailed in the Generic Structure.|
The below is just for example purposes. Reference the Generic Structure for "comics" fields that are optional/required for each type of sale.
The XML feed format should be a single XML structure that contains one or more root elements. Each available element is referenced below.
The following child elements are available for this parent:
|comics Required||This is an array "comic" elements, where each instance represents the comics that are to be fed into GoCollect. The names for each child element are the same as those detailed in the Generic Structure.|
The below is just for example purposes. Reference the Generic Structure for "comics > comic" fields that are optional/required for each type of sale.
CSV is a special format that is only available to a limited retailer audience. Each CSV instance must be manually conected to the retailer's GoCollect account.
The CSV structure simply lists the comics that are available in the retailer's inventory. The first row of the file needs to contain the keys referenced in the Generic Structure. All subsequent rows should contain the details for each of the comics that are to be fed into GoCollect.
The optimal cost structure varies for each business. Our goal is to ensure the GoCollect platform is profitable for you so we offer several, flexible options: