Yurba Docs
Yurba Documentation

Get started

Accounts

Apps

Users

Relationships

Dialogs (Messages)

Tracks (MuseBase)

Photos

Posts

Comments

Safety

Other

Yurba CDN (cdn.yurba.one)

For Desktop Developers

Overview

Learn how to send and receive Yurba social data and how to implement APIs, frameworks, products, and SDKs to suit your application needs.

If you use the Yurba API for flooding, spamming, faking subscriber and view counters, you will be banned forever.


Authorization

For authorization in Yurba, the token value in the header is used.

"token: y.y8ZghPXy6wn2nF55nQ7YCPT1iQb4pkQl"

It is unique for each user and is generated when logging into your account. Most Yurba endpoints do not require any keys other than a token, since they are used directly in the network frontend. More about login

The token is valid indefinitely until it is deleted via the /logout endpoint.

Standardization

To send data to server you should use json format following headers:

"Content-Type: application/json"

The server's response will also be in json format, often with the value ok, which indicates the completion status of your task.

{ ok: 1, id: 1, token: "y.y8ZghPXy6wn2nF55nQ7YCPT1iQb4pkQl" }

In case of error:

{ ok: 0, detail: "auth_failed" }

When it comes to requests, for example, information about the user, the server will return user model.

More about UserModel: /user/{user_tag}