All Verbs | /config |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
AllTiers | form | List<Option> | No | |
AllPostTypes | form | List<Option> | No | |
AllFlagTypes | form | List<Option> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Name | form | string | No | |
Title | form | string | No | |
Value | form | TechnologyTier? | No |
ProgrammingLanguage | Programming Languages |
Client | Client Libraries |
Http | HTTP Server Technologies |
Server | Server Libraries |
Data | Databases and NoSQL Datastores |
SoftwareInfrastructure | Server Software |
OperatingSystem | Operating Systems |
HardwareInfrastructure | Cloud/Hardware Infrastructure |
ThirdPartyServices | 3rd Party APIs/Services |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /config HTTP/1.1
Host: techstacks.io
Accept: application/json
Content-Type: application/json
Content-Length: length
{}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"allTiers":[{"name":"String","title":"String","value":"ProgrammingLanguage"}],"allPostTypes":[{"name":"String","title":"String","value":"ProgrammingLanguage"}],"allFlagTypes":[{"name":"String","title":"String","value":"ProgrammingLanguage"}]}