Properties are used to make authenticated requests against the Janrain APIs. What does that mean and why should that matter to you? These articles should help answer those questions:
The Janrain entity previously-known as API Clients.
Searching for and Filtering Properties
If you have scores (or maybe even hundreds) of properties, this might come in handy.
Copying a Property
If one property is good, then two or more must be better.
Creating a Property
Yes, you can create as many properties as you want. And here's how you do that.
Working with Features
Features are the primary mechanism used to govern property access resources.
Working with IP Whitelists
Specify the devices allowed
to make AI calls using a property.
Working with Client IDs and Client Secrets
Effectively, the username and password for a property.
Renaming a Property
Just in case Property1, Property2, and Property3
don't really cut it.
Help to keep your properties safe, sound, and secure.
Viewing Client Secrets
There's a reason why they're known as secrets. But here's how you can suss them out.
Deleting a Property
Don't want it? Don't need it?
Then get rid of it. (Well, unless it's an Owner property.)
Managing Property Settings
Settings specify such things
as the default flow name and email verification URLs.
Modifying Property Settings
Change your mind about something? Then change the setting value, too.
Adding a Property Setting
Add a custom setting to a property.
Removing a Property Setting
Remove a property-specific setting and rely on the default value instead.