Shop Mobile More Submit  Join Login
COGS #2 by Z-GrimV
We are happy to announce the release of an improved Sta.sh API. After many years the Sta.sh api had become a little confusing and was not keeping up with changes to its backend systems. We therefore decided to redesign parts and fix some of the confusing naming and behaviour.

These changes are versioned so if you are using version prior to 20150416 there will be no change in behaviour, we plan to support the old api for around a year.

Summary of Changes

The folderid and stashid fields have been replaced by stackid and itemid respectively, this change applies to all endpoints.

These endpoints were removed and their functionality is provided by newer ones

  • /stash/folder
  • /stash/media
  • /stash/metadata
  • /stash/move/file
  • /stash/move/folder

New endpoints to manage stacks

  • POST /stash/move/{stackid} - moves stacks
  • POST /stash/position/{stackid} - change the position of a stack within a parent stack
  • POST /stash/update/{stackid} - update stack details (title, description)
  • GET /stash/{stackid} - fetch stack details, returns stash_metadata object
  • GET /stash/{stackid}/contents - list stack contents, supports pagination

New endpoints to manage items

  • GET /stash/item/{itemid} - fetch an item, returns stash_metadata object
  • POST /stash/delete - delete an item by itemid

Stash Metadata object

  • Renamed fields folderid and stashid
  • Removed is_folder
  • Replaced keywords with tags

Any problems can be reported on the GitHub Issue Tracker.

Header artwork: COGS #2 by Z-GrimV


Freeform thumb
FOooo



Freeform embed


Thumb
Sleepy Tobi by muteor
Deviation Embed

Lulu Squidgy Face by muteor
Emotes
Rabbit hole :) (Smile) :D (Big Grin) =P (Razz) Wink/Razz ;) (Wink) :| (Blank Stare) :( (Sad) 
Stash Thumb
Test1 by muteor
Stash Embed
Test1 by muteor
Soundcloud

YouTube
Film





Status

Status Repost


Vimeo

Ustream

SketchFab

Verold

Revision3

COGS #2 by Z-GrimV
After many months of development we are excited to release the all new DeviantArt API. This release includes all the endpoints used in our new mobile apps, adding over 40 new endpoints for your programming pleasure. We hope you enjoy these new features and look forward to seeing the wonderful new things you create.

What's Included?

  • Browse - Access the main browse modes, including More Like This and Journals written by deviants
  • Comments - Access and post user comments
  • Collections - Access collections (favorites)
  • Galleries - Access galleries
  • Feeds - Access various feeds
  • Profiles - Access and manage profile data
  • Friends - Access and manage friends
  • Statuses - Access and post statuses
  • Curated Content - Access our editorial content

Getting Started

You can jump right in by visiting the developer documentation area. Additionally, you will want to read the updated authentication, errors, versioning, and pagination documentation.

Want to try it out right now? You can using the developer console.


Coming Soon

We will be releasing further updates to the API over time. Currently, Message Center and Notes endpoints are omitted. There are plans to include these but they will be released in line with our mobile app releases and after we have reviewed current messaging systems.

Bugs & Feedback

There are many new endpoints so if you find any bugs, we have setup a Github project to report any bugs and feedback can be given in the comments section of this article.

Header artwork: COGS #2 by Z-GrimV


Blah

persoanl journal

Test

Sat Sep 27, 2014, 4:29 PM








I am a lit

I am a lit

Mature Content

This content is intended for mature audiences.


or, enter your birth date.*


Month

Day

Year*
Please enter a valid date format (mm-dd-yyyy)
Please confirm you have reviewed DeviantArt's Terms of Service below.
* We do not retain your date-of-birth information.
xxxx

Mature Content

This content is intended for mature audiences.


or, enter your birth date.*


Month

Day

Year*
Please enter a valid date format (mm-dd-yyyy)
Please confirm you have reviewed DeviantArt's Terms of Service below.
* We do not retain your date-of-birth information.
sdfsadfsadf

API Updates

Tue May 6, 2014, 2:47 AM
We are pleased to announce the release of a new API backend framework and documentation to support future growth of the deviantART & Sta.sh API's.

New Docs2 by muteor

Endpoint2 by muteor



Whats Changed?


We have been busy over the past few months creating a new framework that will allow us to make changes to the API faster.

The main new features are:
  • Versioning - We now support versioning of endpoints meaning we can make backwards incompatible changes.
  • Error Responses - We have standardized our error responses to make it easier for you to handle errors.
  • Request Specifications - We now have fine grained endpoint parameter specifications that improve request validation greatly.
  • Response Specifications - Responses are now predefined so your client will always receive consistent responses and types from the API.
  • Automated Documentation - All of the above means we can auto-generate documentation so that it doesn't become out of sync when we make changes.

Versioning


The ability to version changes to the API is one of the more important new features as it means we can now make backward incompatible changes without breaking older client implementations.

Major versions are specified via the URI of the endpoint and the current major version is v1, for example the whoami call is now: 
/api/v1/oauth2/user/whoami
Minor versions are date based E.g. 20140101 and are requested via the special request header dA-minor-version. If you do not send the header your client will always receive the latest minor version available.

Note: You do NOT need to update your current clients, all requests that do not contain the /v1/ major version in the URI are locked to v1.0 automatically.

Check out the full versioning documentation.

Errors


One of the more inconsistent parts of the old API was its error messages, we have now simplified the error codes and returns to make it easier for your clients to handle error states.

Old style errors are still returned if the request does NOT contain /v1/ in the URI. These will be documented with the endpoint and are marked as deprecated. 

Check out the full errors documentation.

The Future


The point of all this work is to make it possible to release new endpoints in the future. So far we are carefully testing the framework and considering what new endpoints can be released. We don't take the decision to release a new endpoint lightly - it is something that must be well designed, coherent and easy to use and something that we must support for a long time to come.

If you have a burning desire for a particular endpoint that would allow you to do something awesome, then we'd love to hear your thoughts. Please bear in mind that we will only be releasing new endpoints once we are confident that they will work well, be useful to a wide audience and be something we can support log term.

 


...

sdfgsdfg sdgsdfg

Just a test...