API Reference

/watch-to-earn/step/create

post
https://be.namasteapis.com/blockchain/v1/watch-to-earn/step/create

This function creates a step from a task

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
  • RequestCreateStep - This is the request body that will be sent to the API.
double

IGNORE (Will be auto populated)

string

IGNORE (Will be auto populated)

string
enum
required
Allowed:
string
required

[REQUIRED] This is the text that describes the step on the UI. Is between the serial number on the left and button on the right

string
required

[REQUIRED] This is the text goes on the button on the step UI.

boolean

[REQUIRED] This should actually have been called showVideoOnClickingThisButtonBeforeWhateverThisStepActuallyDoes. Because there is a separate VIEW_VIDEO step so don't get confused by this showVideo. It will usually be false almost always.
If not false the videoUrl from this step will be used.

string
boolean

If true user submission will not directly complete the step. The data will be sent to discord verification server and and approval from there alone will complete the step

string

This is the discord webhook url to which the data will be sent for manual verification. Required if discordManualVerification is true

boolean

[INTERNAL USE] Don't fill

boolean

[INTERNAL USE] Will be active in general for most cases. Will be affected by sequentialCompletion flag on the task/job/leaderboard

date-time

Step is valid from this date. Becomes inactive before that. Is probably useful in situations where you want to show "Coming Up"

date-time

Step is valid till this date. Becomes inactive after that. Is probably useful in situations where you want to show "Last date" for an intermediate step.

string
payoutDefinition
payoutDefinitionInput
reward
object
boolean

Disable the step after user has done the step

double

GC Cost to activate this step

otherApiCallsToMake
array of objects

API calls to make on completion of the step

  1. Query params can be specified as so - https://www.google.com/search?outQueryParamName1={inQueryParamName1}&outQueryParamName2={inQueryParamName2}
  2. outQueryParamName1 and outQueryParamName2 are the names that are required by the outgoing api call
  3. inQueryParamName1 and inQueryParamName2 are the names that are parameters that will be picked from the glip window in whatever ways and sent in step submission
  4. Make sure there is no spacing between the curly braces and the query param name in the inQueryParamNameXYZ
otherApiCallsToMake
appLocation
object
required
string
required

To be used for downloading and installing the app

string
string
Headers
string
required
  • This is the API key that is used to authenticate the request.
Responses

401

Unathorized

Updated over 2 years ago

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated over 2 years ago