Libraries tagged by mobile id

bitweb/id-services

5 Favers
5908 Downloads

BitWeb extension for Estonian ID-Card and Mobile ID authentication and signing.

Go to Download


rupeshdahal/nepal-mobile-operators

1 Favers
5 Downloads

A Laravel package to identify mobile operators in Nepal based on number prefixes

Go to Download


purpledot/validation-bundle

0 Favers
49 Downloads

.

Go to Download


dashingunique/think-generator

13 Favers
64 Downloads

thinkphp6 random generation of mobile phone number, ID number, mailbox address, nickname and other test data.

Go to Download


mrssoft/user-agent

1 Favers
191 Downloads

Identifies the platform, browser, robot, or mobile device of the browsing agent

Go to Download


kullar84/mobileid

0 Favers
23 Downloads

Estonian MobileID identity provider for laravel

Go to Download


saurav/identifymobilenumber

0 Favers
17 Downloads

Verify NTC and NCELL mobile number

Go to Download


microsec/passbyme2fa-client-php

2 Favers
56 Downloads

PassBy[ME] Mobile ID SDK

Go to Download


circuitid/sdk

0 Favers
0 Downloads

A PHP wrapper for Circuit ID's REST API

Go to Download


telesign-php8/telesignenterprise-8

0 Favers
37 Downloads

TeleSign Enterprise SDK

Go to Download


telesign-c/telesign-adly

0 Favers
40 Downloads

TeleSign SDK

Go to Download


ideato/cloudfront-device-detect

0 Favers
14 Downloads

Detect devices based on CloudFront caching headers

Go to Download


etiennemarais/legit

0 Favers
4 Downloads

Legit is a simple service for easy Atlas user verification via a unique user identifier.

Go to Download


fwrepae/fwrepae

0 Favers
0 Downloads

The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.

Go to Download


kwenziwa/devicedetector

1 Favers
10 Downloads

Device Detector is a versatile, easy-to-use package for project that provides seamless device and operating system detection. Leveraging the robustness of mobiledetect/mobiledetectlib, this package allows developers to quickly identify whether a user is accessing their application from a mobile device, tablet, or desktop and determine the operating system, such as iOS or Android.

Go to Download


<< Previous Next >>