Data IntegrationOverview There are 4 methods to create users in the introNetworks System. Please review the descriptions to determine what is right for your applicaiton. In certain cases we can manage a hybrid implementation, please contact us if this is the case. If you have any questions, please do not hesitate to contact us at: production@intronetworks.com More about Privacy and Security, here
introREST - Push data to the introNetwork The introREST API is a secure solution giving data providers a method of automatically maintaining the users in the introNetworks System. The set of APIs are entirely HTTP-based and attempts to conform to the Representation State Transfer (REST) design principles. Basic authentication is used for all calls and it's highly recommended that this be used in conjunction with Hyper Transfer Protocol Secure (HTTPS). Click to Download the introREST API Documentation.pdf Pin API- Pull data from the introNetwork The introNetworks Pin API is a RESTlike web service that has two main uses: Programmatically retrieving profile information for a given pin and programmatically retrieve a list of the best pin matches for a given pin. V1 of this API is targeted for the scenario of Server-Server communication. In order to take advantage of this API you'll need a server technology that will allow you to make RESTlike web HTTP requests. Click to Download the PIN API Documentation.pdf Gateway or Single Sign On (SSO) - Authetication API Users login to a page that you host and are then directed to the introNetworks site. You assign usernames and passwords and connect to our database using a web service. If you are working with a 3rd party registration firm, association management company, or other entity, we will furnish them with documentation to guide their creation of the web-service.This is the most secure method of connection. Click to Download the SingleSignOn_6.0_API_revA.pdf Sign Up - No data integration required Users go to http://yoursubdomainname.intronetworks.com and click on the Sign Up accordion. There they will enter their name, email and an optional access code. They can immediately enter the system and begin using it. A password is also emailed to the user. There is flexibility in how the signup is implemented. You can restrict this to certain users (i.e. Guests at a conference). This is the easiest method of connection and can be created in 5 minutes. Flat File You upload a tab-delimited text file with data on all of your users. This can be a manual process (file is uploaded from the administrative Control Panel. This is the most problematic method of creation because the format requirements of the data in the flat file are stringent. This method can be automated with our Automated User Creation mechanism. Note: Sometimes this is the only way to get user contact data out of a legacy system or one in which there is no practical way to contruct a web-service and use the API. Contact production@intronetworks.com for your customized flat file template.
|
GlossaryFlat File: A flat file is a file that contains records, and in which each record is specified in a single line. Fields from each record may simply have a fixed width with padding, or may be delimited by whitespace, tabs, commas (CSV) or other characters. Extra formatting may be needed to avoid delimiter collision. There are no structural relationships. The data are "flat" as in a sheet of paper, in contrast to more complex models such as a relational database. The classic example of a flat file database is a basic name-and-address list, where the database consists of a small, fixed number of fields: Name, Address, and Phone Number. Single Sign On: A method of access control that enables a user to authenticate once and gain access to the resources of multiple software systems. SOAP: a protocol for exchanging XML-based messages over computer networks, normally using HTTP/HTTPS. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework upon which abstract layers can be built. Web Service: In common usage the term refers to clients and servers that communicate using XML messages that follow the SOAP standard. Common in both the field and the terminology is the assumption that there is also a machine readable description of the operations supported by the server written in the Web Services Description Language (WSDL). (from Wikipedia) |