This section makes reference to various API calls. Click here for the full technical documentation related to those requests.
As far as the WrapDapp ecosystem is concerned, Publishers and Providers are the same thing, ie, any entity that represents and distributes music on behalf of a songwriter or artist.
A "Publisher" is any large entity with a catalog of owned music, such as "Sony Music" or "Universal Music Group".
A provider distributes music on behalf of artists, however they may not own the rights to that music. Examples of these services include "CD Baby", "Tunecore", "iMusician" or "Distrokid".
Working Email Required!
It is important to include
a
working
email when creating the
user, otherwise we will not have a means by which to contact the user with
instructions on how to claim
ownership over their wallet (IE, NFTs).
Wallet Notice
Every new user not matching an existing
localUserId
in our system
will result in a new wallet being generated for the user.
POST/user
endpoint to
create a user.localUserId
(somethings
referred to as the providerUserId
as well) input
matches
the internal ID within your system; this can be used in the future
to get an
internal WrapDapp user ID based on the known user ID in your platform.
NFT Minting Notice
This flow does not mint an NFT,
send an
audio-fingerprint to the chain, or create any chain
syncs against song metadata. Additional requests are required for those actions.
GET/user/provider/{providerUserId}
endpoint if you didn't save it initially. This endpoint will return an
id
field matching the user's WrapDapp User ID.
POST/user/{userId}song
endpoint
with the song's details.
While this feature is on our roadmap and will be added soon, as or now the best
way to add artists into WrapDapp is to use the POST/user
endpoint.
While this feature is on our roadmap and will be added soon, as or now the best
way to add songs into WrapDapp is to use the POST/user/{userId}song
endpoint.